Re: Position Papers Guidelines for W3C Workshop

I encourage you to actively seek out a moderate/open-minded person from the 
"prefers plain-text email" camp.  Such people may not be motivated to attend a 
workshop on HTML email without an active invitation, but those are the people 
you need to get on board to get broader deployment of HTML email.

In the event that IETF-related standards work in the IMAP/SMTP/MIME area would 
assist the deployability/usability of HTML email, I am open to such proposals. 
It's quite possible that MHTML (RFC 2557) needs some additional work to deploy 
more successfully.

                - Chris Newman
                IETF Applications Area Director

Karl Dubost wrote on 4/25/07 10:36 +0900:
> Sorry to be a bit late on this, I had a lot on my plate last week. A
> position paper is nothing complicated.
>
>
> # Content
> Position papers will be the basis for the discussion at the workshop.  Papers
> should explain the participant's interest in the workshop,  explain their
> position and include concrete examples of their  suggestions.
>
> # Language and Materials
> Position papers should be written in English. Examples may be  illustrated
> with non-English languages with an English explanation.
> You can join illustrations, schemas, and graphics too.
>
> # Format
> All papers should be 1 to 5 pages, although they may link to longer  versions
> or appendices. Allowed formats are valid HTML or XHTML, or  plain text.
> HTML, XHTML is preferred
>
>
> --
> Karl Dubost - http://www.w3.org/People/karl/
> W3C Conformance Manager, QA Activity Lead
>    QA Weblog - http://www.w3.org/QA/
>       *** Be Strict To Be Cool ***
>
>
>
>
>

Received on Wednesday, 25 April 2007 23:23:22 UTC